Skip to content

governance: Add member, reviewer and committer roles#43

Closed
jmarrero wants to merge 1 commit into
bootc-dev:mainfrom
jmarrero:governance-roles
Closed

governance: Add member, reviewer and committer roles#43
jmarrero wants to merge 1 commit into
bootc-dev:mainfrom
jmarrero:governance-roles

Conversation

@jmarrero

@jmarrero jmarrero commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Add three new contributor ladder tiers to the governance document: member, reviewer and committer. All existing maintainers are listed as committers in MAINTAINERS.md.

This was drafted using Opus 4.6 and with https://kubernetes.io/docs/contribute/participate/roles-and-responsibilities/ & https://github.com/containerd/.project/blob/main/GOVERNANCE.md as examples. Iterated a bit to make sure Opus did not rewrite everything and just added the relevant sections.

DRAFT while we discuss

Add three new contributor ladder tiers to the governance document:
member, reviewer and committer. All existing maintainers are listed
as committers in MAINTAINERS.md.

Signed-off-by: Joseph Marrero Corchado <[email protected]>
Comment thread GOVERNANCE.md
issues and pull requests, and their LGTM counts towards the required LGTM count
to merge a code change into the project.

Reviewers are part of the organization but do not have write access. Becoming a

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is "write" access equivalent to the Github default? As is today "write" implies the ability to e.g. add labels, close issues etc.

Some custom work will be necessary to implement this "can review but almost nothing else" flow. It also feels weird if they can review and hence merge code but not manage issues.

It seems a lot simpler to not create that distinction unless we say a Reviewer can approve a PR from a maintainer, but not an arbitrary other one. That would itself require some custom logic, but makes a bit more sense to me?


Well, I guess this came from containerd, we should try to see how they implement this

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The agent thinks we can do something like:

- Create two GitHub teams in the bootc-dev org: e.g. committers and reviewers
- Give both teams Write access to repos
- Enable branch protection on main with "Restrict who can push to matching branches" and only add the committers team
- Reviewers can approve PRs and their approval satisfies the "required approvals" check, but only Committers can click merge / add to merge queue

But I need to check this on my own org/repos.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

containerd also uses kubernetes-prow so that might be doing some of the heavy lifting too.

@nimbinatus

Copy link
Copy Markdown
Member

Tagging in that there's more discussion in #22

@jmarrero

jmarrero commented Jul 9, 2026

Copy link
Copy Markdown
Contributor Author

Let's just use #22 for this.

@jmarrero jmarrero closed this Jul 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants